i4target [ -h ] [ -O ] [ -V ] [ -o ] [ -l ] [ -v ]
To create LicensePower/iFOR licenses for an application, an application supplier will need the target ID of the machine where the LicensePower/iFOR licenses will be installed. The target ID tool (i4target) should be run on the machine where you want to identify an LicensePower/iFOR target ID. For server-based licensing, this will be the machine that is executing the license server (i4lmd) where you plan to install this application supplier's licenses. For nodelocked licensing, this will be the system where the application will be executing.
The algorithm that is used to identify an LicensePower/iFOR target ID may vary depending on operating system platform.
For example: On an NEC system the targetid is derived from the command (/usr/necbin/getsystemid).
For example: On an HP-UX machine licenses managed by the i4lmd (concurrent and use once licenses), the LicensePower/iFOR target ID is derived from the link level address of the LAN card accessed by the device file /dev/i4target on the machine that is running the i4lmd. If /dev/i4target does not exist and the super-user is executing i4target, i4target will create /dev/i4target. On an HP 9000 Series 700 or 800, the device file will be for the lan0 LAN card. This is the same method used by the i4lmd for determining the LicensePower/iFOR ID of the machine on which it is executing.
On HP-UX, for LicensePower/iFOR nodelocked licenses, the LicensePower/iFOR ID is derived from:
i4target